fix(rag): eliminate source-backed latency tails#845
Conversation
Keep broad agitation retrieval on one lexical RPC, bypass the repeated LAI model timeout only after deterministic quality validation, and align the single-source safety-plan canary with its required source contract.\n\nVerified with the offline RAG contract (21 files, 272 tests) and focused live read-only evaluations.
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughClinical search recognizes broader medication-chart requests and uses fallback medication vocabulary when explicit dose or route terms are absent. Routine extractive recovery records a specific route reason, while generic LAI-management matching remains unchanged. ChangesMedication-chart search expansion
Extractive recovery route tagging
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #3269 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Pull request was closed
Summary
generic LAI managementqueries when deterministic evidence gates already pass.Verification
git diff --check(pass)npm run verify:pr-local(not run: local dependencies are not installed in this worktree; node_modules/vitest/vitest.mjs missing. Re-run once dependencies are installed.)npm run eval:retrieval:quality(provider/API-required and blocked in this environment without confirmed live credentials)npm run check:production-readiness(not run: no runtime/provider-only production checks requested for this handoff)Risk and rollout
Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Notes
Summary by CodeRabbit